Date: Sun, 2 Oct 94 04:30:01 PDT From: Advanced Amateur Radio Networking Group Errors-To: TCP-Group-Errors@UCSD.Edu Reply-To: TCP-Group@UCSD.Edu Precedence: List Subject: TCP-Group Digest V94 #217 To: tcp-group-digest TCP-Group Digest Sun, 2 Oct 94 Volume 94 : Issue 217 Today's Topics: need wampes info Send Replies or notes for publication to: . Subscription requests to . Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the TCP-Group Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: Sat, 1 Oct 94 12:48:26 -0600 From: "Robert E. Brose II" Subject: need wampes info If possible, I'd like to get some help from some of the WAMPES users out there. I can run WAMPES fine. I have it running in an X window running 3 radio interfaces and a slip port looped backed into the unix box to connect to the unix tcp/ip. The 2 changes I'd like to make are: 1) free up the serial ports used to loop the tcp into the unix box. I've heard there is a way to do this with pty's but have seen no examples. 2) run WAMPES in the background and then use cnet to access it. It would be nice to simply startup WAMPES when the normal tcp starts up on the unix box so that if the power goes down, when it comes back on, the machine comes back up and brings the gateways back online. I've tried the example in the doc, net /tcp/startup